| Redis Cluster 介紹 | 您所在的位置：网站首页 › redis cluster create › Redis Cluster 介紹 |
Redis Cluster 介紹
前言在巨量資料下，資料庫合理的分片(DB sharding)可以幫助我們承受更高量的資料量(前提Index還有設定都調教到很好在考慮 sharding) 而在 Redis 世界裡也有 redis cluster 來做 sharding 事情，今天就來跟大家分享介紹 我使用是 bitnami redis-cluster 這個 Image 來做這次 Poc 此案例是 3 master - 3 slave Redis server 範例 建立 Redis ClusterHow to Use1docker-compose up -d跑完之後就會出現 6 台 Redis Container，如下表 12345678$ docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES1a0c740cbb96 bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 31 seconds ago Up 27 seconds 0.0.0.0:8105->6379/tcp, :::8105->6379/tcp rediscluster_redis-node-5_11651a81a286f bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 37 seconds ago Up 30 seconds 0.0.0.0:8102->6379/tcp, :::8102->6379/tcp rediscluster_redis-node-2_15d93edfc55e6 bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 37 seconds ago Up 31 seconds 0.0.0.0:8104->6379/tcp, :::8104->6379/tcp rediscluster_redis-node-4_18ab5bbbb7364 bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 37 seconds ago Up 29 seconds 0.0.0.0:8103->6379/tcp, :::8103->6379/tcp rediscluster_redis-node-3_18edf90bed3fb bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 37 seconds ago Up 29 seconds 0.0.0.0:8101->6379/tcp, :::8101->6379/tcp rediscluster_redis-node-1_1e11ac0ec56aa bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 37 seconds ago Up 30 seconds 0.0.0.0:8100->6379/tcp, :::8100->6379/tcp rediscluster_redis-node-0_1 查看 Redis Cluster 架構我們進入 rediscluster_redis-node-0_1 這台Container 利用 redis-cli 輸入 CLUSTER INFO 可以查看目前 Cluster 基本狀態 1234567891011121314151617181920$ docker exec -it rediscluster_redis-node-0_1 bash/$ redis-cli -a redisCluster127.0.0.1:6379> CLUSTER INFOcluster_state:okcluster_slots_assigned:16384cluster_slots_ok:16384cluster_slots_pfail:0cluster_slots_fail:0cluster_known_nodes:6cluster_size:3cluster_current_epoch:6cluster_my_epoch:1cluster_stats_messages_ping_sent:1723cluster_stats_messages_pong_sent:1833cluster_stats_messages_sent:3556cluster_stats_messages_ping_received:1828cluster_stats_messages_pong_received:1723cluster_stats_messages_meet_received:5cluster_stats_messages_received:3556本篇我 redis password 統一使用 redisCluster 所以進入 redis 操作之前記得輸入 -a 跟密碼 進入可以看到幾個重要資訊 cluster_state cluster_size:3 cluster_current_epoch:6 cluster_slots_assigned代表目前 Cluster 啟動狀態OK，再來我們利用 --cluster check 了解該 Redis Server Cluster 中 master-slave 跟各節點對應關係 1redis-cli --cluster check 127.0.0.1:6379 -a redisCluster結果如下 123456789101112131415161718192021222324252627282930/$ redis-cli --cluster check 172.22.0.3:6379 -a redisCluster172.22.0.5:6379 (7186bbf7...) -> 0 keys | 5462 slots | 1 slaves.172.22.0.2:6379 (3decf740...) -> 0 keys | 5461 slots | 1 slaves.172.22.0.4:6379 (ee76b9f8...) -> 0 keys | 5461 slots | 1 slaves.[OK] 0 keys in 3 masters.0.00 keys per slot on average.>>> Performing Cluster Check (using node 172.22.0.3:6379)S: 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 172.22.0.3:6379 slots: (0 slots) slave replicates 3decf740935f98a40d2d73416937e63abc3f4781M: 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5f 172.22.0.5:6379 slots:[5461-10922] (5462 slots) master 1 additional replica(s)M: 3decf740935f98a40d2d73416937e63abc3f4781 172.22.0.2:6379 slots:[0-5460] (5461 slots) master 1 additional replica(s)M: ee76b9f8f8c261918b44caf856070acab1a5072a 172.22.0.4:6379 slots:[10923-16383] (5461 slots) master 1 additional replica(s)S: c93879a2f37ab14b9bb25f54a8e856a2526e4621 172.22.0.7:6379 slots: (0 slots) slave replicates 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5fS: bbeafa6b1e703035c364a2d0f476951268d0a9ff 172.22.0.6:6379 slots: (0 slots) slave replicates ee76b9f8f8c261918b44caf856070acab1a5072a[OK] All nodes agree about slots configuration.>>> Check for open slots...>>> Check slots coverage...[OK] All 16384 slots covered.依照上面資訊我們可以畫出架構如圖
redis 幫我們分配 master 對應 slave 並沒有特別順序，所以你建立的跟我建立很可能不一樣 我們可以在透過下面命令顯示 container 對應使用 ip 12345678$ docker inspect -f '{{.Name}} - {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $(docker ps -q)/rediscluster_redis-node-5_1 - 172.22.0.7/rediscluster_redis-node-2_1 - 172.22.0.4/rediscluster_redis-node-4_1 - 172.22.0.3/rediscluster_redis-node-3_1 - 172.22.0.6/rediscluster_redis-node-1_1 - 172.22.0.5/rediscluster_redis-node-0_1 - 172.22.0.2使用上面命令可以更好理解，Container Name之間對應關係 在 Redis Clsuter 新增 key 注意事項我進入其中一台 master container rediscluster_redis-node-0_1 123456789101112/$ redis-cli -h 172.22.0.2 -a redisCluster172.22.0.2:6379> set k1 1(error) MOVED 12706 172.22.0.4:6379172.22.0.2:6379> set k2 1OK172.22.0.2:6379> set k3 1OK172.22.0.2:6379> set k4 1(error) MOVED 8455 172.22.0.5:6379172.22.0.2:6379> set k5 1(error) MOVED 12582 172.22.0.4:6379使用 get 拿資料時發現我們只拿的到 k2,k3 的資料 12345678910172.22.0.2:6379> get k1(error) MOVED 12706 172.22.0.4:6379172.22.0.2:6379> get k2"1"172.22.0.2:6379> get k3"1"172.22.0.2:6379> get k4(error) MOVED 8455 172.22.0.5:6379172.22.0.2:6379> get k5(error) MOVED 12582 172.22.0.4:6379我們可以透過 CLUSTER KEYSLOT {key} 來算出我們 key 算出來的 slot 數值 12345678910172.22.0.2:6379> CLUSTER KEYSLOT k1(integer) 12706172.22.0.2:6379> CLUSTER KEYSLOT k2(integer) 449172.22.0.2:6379> CLUSTER KEYSLOT k3(integer) 4576172.22.0.2:6379> CLUSTER KEYSLOT k4(integer) 8455172.22.0.2:6379> CLUSTER KEYSLOT k5(integer) 12582因為我們是進入 172.22.0.2 這台 Redis server 操作 我們只能操作屬於我們 slot 也就是介於 [0-5460] slot 資料，所以只有 k2,k3 符合
那你會想這樣不就跟單機操作一樣，別急讓我來說怎麼正確使用 Redis Cluster 我們先退出當前 redis-cli 操作 redis-cli -h 172.22.0.2 -a redisCluster -c 在此輸入並在最後多一個參數 -c -c 代表是要使用 cluster 操作 在執行 set {key} {value} 命令，會發現已經沒有 error 但取而代之是 Redirected to slot 那是因為 -c 模式下會幫我們在資料寫入前轉到該 slot redis server node 中在執行命令. 所以能發現出現 Redirected to slot Redis server ip 就會改變 12345678910111213141516/$ redis-cli -h 172.22.0.2 -a redisCluster -c172.22.0.2:6379> set k1 1-> Redirected to slot [12706] located at 172.22.0.4:6379OK172.22.0.4:6379> set k2 1-> Redirected to slot [449] located at 172.22.0.2:6379OK172.22.0.2:6379> set k3 1OK172.22.0.2:6379> set k4 1-> Redirected to slot [8455] located at 172.22.0.5:6379OK172.22.0.5:6379> set k5 1-> Redirected to slot [12582] located at 172.22.0.4:6379OK所以在操作 Redis cluster 記得要使用 cluster 操作模式 擴充 Redis Cluster假如因為業務需求流量突然進來我們想在目前 Cluster 多開幾組 master-slave redis 怎辦? 這邊跟大家來分享如何多加 redis 進入 Cluster 中 擴充步驟 在 redis-cluster 中新增多組(或一組) master-slave redis 將新建立 master container 加入 Cluster 中 把目前 Cluster slot 分配給 剛建立 master container (如果可以最好 slot 數量平均) 將新建立 slave container 掛入新建立 master container 上在 redis-cluster 中新增多組(或一組) master-slave redis，使用下面命令 因為在使用 docker-compose 啟動時已經幫我們建立一個 network 所以我們需要指定新加的兩個 Container 在 rediscluster_default 中這樣他們才可以訪問的到 123docker run -d --name redis-new-master01 --network rediscluster_default --privileged=true -p 8106:6379 redis:6.2 --cluster-enabled yes --appendonly yes --requirepass "redisCluster"docker run -d --name redis-new-slave01 --network rediscluster_default --privileged=true -p 8107:6379 redis:6.2 --cluster-enabled yes --appendonly yes --requirepass "redisCluster"在利用 docker ps 我們發現剛建立的兩個 Container 已經建立完畢 12345678910111213141516171819CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESe2c017e625db redis:6.2 "docker-entrypoint.s…" 4 seconds ago Up 3 seconds 0.0.0.0:8107->6379/tcp, :::8107->6379/tcp redis-new-slave010bc645dc5ba8 redis:6.2 "docker-entrypoint.s…" 11 seconds ago Up 9 seconds 0.0.0.0:8106->6379/tcp, :::8106->6379/tcp redis-new-master011a0c740cbb96 bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 3 hours ago Up 3 hours 0.0.0.0:8105->6379/tcp, :::8105->6379/tcp rediscluster_redis-node-5_11651a81a286f bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 3 hours ago Up 3 hours 0.0.0.0:8102->6379/tcp, :::8102->6379/tcp rediscluster_redis-node-2_15d93edfc55e6 bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 3 hours ago Up 3 hours 0.0.0.0:8104->6379/tcp, :::8104->6379/tcp rediscluster_redis-node-4_18ab5bbbb7364 bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 3 hours ago Up 3 hours 0.0.0.0:8103->6379/tcp, :::8103->6379/tcp rediscluster_redis-node-3_18edf90bed3fb bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 3 hours ago Up 3 hours 0.0.0.0:8101->6379/tcp, :::8101->6379/tcp rediscluster_redis-node-1_1e11ac0ec56aa bitnami/redis-cluster:6.2 "/opt/bitnami/script…" 3 hours ago Up 3 hours 0.0.0.0:8100->6379/tcp, :::8100->6379/tcp rediscluster_redis-node-0_1$ docker inspect -f '{{.Name}} - {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $(docker ps -q)/redis-new-slave01 - 172.22.0.9/redis-new-master01 - 172.22.0.8/rediscluster_redis-node-5_1 - 172.22.0.7/rediscluster_redis-node-2_1 - 172.22.0.4/rediscluster_redis-node-4_1 - 172.22.0.3/rediscluster_redis-node-3_1 - 172.22.0.6/rediscluster_redis-node-1_1 - 172.22.0.5/rediscluster_redis-node-0_1 - 172.22.0.2查詢到 redis-new-master01 使用 IP 我們可以利用 --cluster add-node 將新的 master node 加入 cluster 中 1redis-cli --cluster add-node 172.22.0.8:6379 172.22.0.2:6379 -a redisCluster加入成功後我們在利用 --cluster check 命令查詢 Cluster 資訊，會看到目前多了一筆資料 172.22.0.8:6379 (0885f85b...) -> 0 keys | 0 slots | 0 slaves. 下一步就需要分配 slot 給這個 master 123456789101112131415161718192021222324252627282930313233/$ redis-cli --cluster check 172.22.0.3:6379 -a redisCluster172.22.0.5:6379 (7186bbf7...) -> 1 keys | 5462 slots | 1 slaves.172.22.0.2:6379 (3decf740...) -> 2 keys | 5461 slots | 1 slaves.172.22.0.4:6379 (ee76b9f8...) -> 2 keys | 5461 slots | 1 slaves.172.22.0.8:6379 (0885f85b...) -> 0 keys | 0 slots | 0 slaves.[OK] 5 keys in 4 masters.0.00 keys per slot on average.>>> Performing Cluster Check (using node 172.22.0.3:6379)S: 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 172.22.0.3:6379 slots: (0 slots) slave replicates 3decf740935f98a40d2d73416937e63abc3f4781M: 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5f 172.22.0.5:6379 slots:[5461-10922] (5462 slots) master 1 additional replica(s)M: 3decf740935f98a40d2d73416937e63abc3f4781 172.22.0.2:6379 slots:[0-5460] (5461 slots) master 1 additional replica(s)M: ee76b9f8f8c261918b44caf856070acab1a5072a 172.22.0.4:6379 slots:[10923-16383] (5461 slots) master 1 additional replica(s)S: c93879a2f37ab14b9bb25f54a8e856a2526e4621 172.22.0.7:6379 slots: (0 slots) slave replicates 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5fM: 0885f85b94f8ddc186f1eac8f532be532fb7f5b1 172.22.0.8:6379 slots: (0 slots) masterS: bbeafa6b1e703035c364a2d0f476951268d0a9ff 172.22.0.6:6379 slots: (0 slots) slave replicates ee76b9f8f8c261918b44caf856070acab1a5072a[OK] All nodes agree about slots configuration.>>> Check for open slots...>>> Check slots coverage...[OK] All 16384 slots covered.目前要做的是把當前 Cluster 上 master 上的 slot 分配給，剛建立 master container，達到資料分擔 我們可以透過 redis-cli --cluster reshard {被分配 Redis Cluster 節點 IP}，由上面資訊得知新建立 master id 是 172.22.0.8:6379 1redis-cli --cluster reshard 172.22.0.8:6379 -a redisCluster執行後我們會被詢問要轉移多少 slot 數量給新的 master，我們知道 Redis Cluster 有 16384 個 slot 所以為了平均分配 16384/4 = 4096 How many slots do you want to move (from 1 to 16384) 我們可以輸入 4096 What is the receiving node ID? 我們由上面資訊知道 新建立 master id 是 0885f85b94f8ddc186f1eac8f532be532fb7f5b1最後可以輸入 all 就會開始分配 slot 1234Please enter all the source node IDs. Type 'all' to use all the nodes as source nodes for the hash slots. Type 'done' once you entered all the source nodes IDs.Source node #1: all跑完後我們利用 redis-cli --cluster check 172.22.0.8:6379 -a redisCluster 查詢可以看到 slot 已經平均分配到四個 master 上面了 12345678910111213141516171819202122232425262728293031172.22.0.8:6379 (0885f85b...) -> 1 keys | 4096 slots | 0 slaves.172.22.0.4:6379 (ee76b9f8...) -> 2 keys | 4096 slots | 1 slaves.172.22.0.2:6379 (3decf740...) -> 1 keys | 4096 slots | 1 slaves.172.22.0.5:6379 (7186bbf7...) -> 1 keys | 4096 slots | 1 slaves.[OK] 5 keys in 4 masters.0.00 keys per slot on average.>>> Performing Cluster Check (using node 172.22.0.8:6379)M: 0885f85b94f8ddc186f1eac8f532be532fb7f5b1 172.22.0.8:6379 slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) masterM: ee76b9f8f8c261918b44caf856070acab1a5072a 172.22.0.4:6379 slots:[12288-16383] (4096 slots) master 1 additional replica(s)M: 3decf740935f98a40d2d73416937e63abc3f4781 172.22.0.2:6379 slots:[1365-5460] (4096 slots) master 1 additional replica(s)S: c93879a2f37ab14b9bb25f54a8e856a2526e4621 172.22.0.7:6379 slots: (0 slots) slave replicates 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5fS: bbeafa6b1e703035c364a2d0f476951268d0a9ff 172.22.0.6:6379 slots: (0 slots) slave replicates ee76b9f8f8c261918b44caf856070acab1a5072aS: 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 172.22.0.3:6379 slots: (0 slots) slave replicates 3decf740935f98a40d2d73416937e63abc3f4781M: 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5f 172.22.0.5:6379 slots:[6827-10922] (4096 slots) master 1 additional replica(s)[OK] All nodes agree about slots configuration.>>> Check for open slots...>>> Check slots coverage...[OK] All 16384 slots covered.最後一步就是把 新的 slave redis 掛載到剛剛的 master redis 上 我們可以利用下面命令 template 來處理 1redis-cli --cluster add-node {new-slave-redis IP} {cluster-redis IP} --cluster-slave --cluster-master-id 新節點master-id -a redisCluster轉換成可執行命令如下 1redis-cli --cluster add-node 172.22.0.9:6379 172.22.0.8:6379 --cluster-slave --cluster-master-id 0885f85b94f8ddc186f1eac8f532be532fb7f5b1 -a redisCluster看到下面執行結果代表掛載成功 12345678910//...[OK] All nodes agree about slots configuration.>>> Check for open slots...>>> Check slots coverage...[OK] All 16384 slots covered.>>> Send CLUSTER MEET to node 172.22.0.9:6379 to make it join the cluster.Waiting for the cluster to join>>> Configure node as replica of 172.22.0.8:6379.[OK] New node added correctly.全部執行完後結果，我們就有四個節點可以存放 Redis 資料
處理完後 Redis Cluster 架構圖就如下
假如我們原本想要平均分配每個 master node slot 數量，但不小心設定錯誤可以使用 --cluster rebalance 來重新分配 slot 數量，讓每個 master 得到平衡的 slot 數量 1redis-cli --cluster rebalance 172.21.0.8:6379 -a redisCluster 縮容 Redis Cluster縮容 Redis Cluster 也有相對應步驟，步驟跟擴容相反步驟 將 slave Redis container 移除 Cluster 並刪除 清出 master Redis container slot 數量並重新分配 (確保此 master Redis 沒有對應 slot ) 刪除 master Redis container slot本次目標要把 Master1-Slave1 移除 Cluster
將slave Redis container 移除 Cluster 並刪除，我們可以執行下面命令 1redis-cli --cluster del-node {要刪除的 Redis IP} {要刪除的 Redis ID} -a redisCluster在刪除前先查看資訊 Cluster 資訊 123456789101112131415161718192021222324252627282930313233/$ redis-cli --cluster check 172.22.0.4:6379 -a redisCluster172.22.0.5:6379 (7186bbf7...) -> 1 keys | 4096 slots | 1 slaves.172.22.0.2:6379 (3decf740...) -> 1 keys | 4096 slots | 1 slaves.172.22.0.4:6379 (ee76b9f8...) -> 2 keys | 4096 slots | 1 slaves.172.22.0.8:6379 (0885f85b...) -> 1 keys | 4096 slots | 1 slaves.[OK] 5 keys in 4 masters.0.00 keys per slot on average.>>> Performing Cluster Check (using node 172.22.0.3:6379)S: 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 172.22.0.3:6379 slots: (0 slots) slave replicates 3decf740935f98a40d2d73416937e63abc3f4781M: 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5f 172.22.0.5:6379 slots:[6827-10922] (4096 slots) master 1 additional replica(s)M: 3decf740935f98a40d2d73416937e63abc3f4781 172.22.0.2:6379 slots:[1365-5460] (4096 slots) master 1 additional replica(s)S: 0abc62f3da4a649a5dea58739e6c087bf52c387f 172.22.0.9:6379 slots: (0 slots) slave replicates 0885f85b94f8ddc186f1eac8f532be532fb7f5b1M: ee76b9f8f8c261918b44caf856070acab1a5072a 172.22.0.4:6379 slots:[12288-16383] (4096 slots) master 1 additional replica(s)S: c93879a2f37ab14b9bb25f54a8e856a2526e4621 172.22.0.7:6379 slots: (0 slots) slave replicates 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5fM: 0885f85b94f8ddc186f1eac8f532be532fb7f5b1 172.22.0.8:6379 slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master 1 additional replica(s)S: bbeafa6b1e703035c364a2d0f476951268d0a9ff 172.22.0.6:6379 slots: (0 slots) slave replicates ee76b9f8f8c261918b44caf856070acab1a5072a確認要刪除 Redis 資訊是 172.22.0.3:6379 跟 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 12345/$ redis-cli --cluster del-node 172.22.0.3:6379 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 -a redisCluster>>> Removing node 2c25a1a5d1cb1ba780170685c4f39dfe6f0da8f0 from cluster 172.22.0.3:6379>>> Sending CLUSTER FORGET messages to the cluster...>>> Sending CLUSTER RESET SOFT to the deleted node.刪除 slave1 之後能發現 master1 原本對應的 slave 已經不見了
這次轉移 master slot 我使用 reshard 另一種寫法 123456789101112redis-cli --cluster reshard 172.22.0.2:6379 \--cluster-from 3decf740935f98a40d2d73416937e63abc3f4781 \--cluster-to 0885f85b94f8ddc186f1eac8f532be532fb7f5b1 \--cluster-slots 4096 \--cluster-yes \-a redisCluster172.22.0.4:6379 (ee76b9f8...) -> 2 keys | 4096 slots | 1 slaves.172.22.0.8:6379 (0885f85b...) -> 2 keys | 8192 slots | 1 slaves.172.22.0.5:6379 (7186bbf7...) -> 1 keys | 4096 slots | 1 slaves.172.22.0.2:6379 (3decf740...) -> 0 keys | 0 slots | 0 slaves.執行完後發現到 172.22.0.2:6379 身上已經沒有其他 Slot 了，之後可以利用上面說到 rebalance 命令來重新分配 slot 123456redis-cli --cluster rebalance 172.22.0.4:6379 -a redisCluster172.22.0.4:6379 (ee76b9f8...) -> 3 keys | 5462 slots | 1 slaves.172.22.0.8:6379 (0885f85b...) -> 1 keys | 5461 slots | 1 slaves.172.22.0.5:6379 (7186bbf7...) -> 1 keys | 5461 slots | 1 slaves.172.22.0.2:6379 (3decf740...) -> 0 keys | 0 slots | 0 slaves.分配完後結果如上 最後我們就可以執行最後一步：刪除 master redis 使用 --cluster del-node 命令即可 123456789101112131415161718192021222324252627redis-cli --cluster del-node 172.22.0.2:6379 3decf740935f98a40d2d73416937e63abc3f4781 -a redisCluster172.22.0.4:6379 (ee76b9f8...) -> 3 keys | 5462 slots | 1 slaves.172.22.0.8:6379 (0885f85b...) -> 1 keys | 5461 slots | 1 slaves.172.22.0.5:6379 (7186bbf7...) -> 1 keys | 5461 slots | 1 slaves.[OK] 5 keys in 3 masters.0.00 keys per slot on average.>>> Performing Cluster Check (using node 172.22.0.4:6379)M: ee76b9f8f8c261918b44caf856070acab1a5072a 172.22.0.4:6379 slots:[0-1365],[12288-16383] (5462 slots) master 1 additional replica(s)M: 0885f85b94f8ddc186f1eac8f532be532fb7f5b1 172.22.0.8:6379 slots:[2731-6826],[10923-12287] (5461 slots) master 1 additional replica(s)S: c93879a2f37ab14b9bb25f54a8e856a2526e4621 172.22.0.7:6379 slots: (0 slots) slave replicates 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5fS: bbeafa6b1e703035c364a2d0f476951268d0a9ff 172.22.0.6:6379 slots: (0 slots) slave replicates ee76b9f8f8c261918b44caf856070acab1a5072aM: 7186bbf7a1689d66c94a448cb1a197a7bd9b9e5f 172.22.0.5:6379 slots:[1366-2730],[6827-10922] (5461 slots) master 1 additional replica(s)S: 0abc62f3da4a649a5dea58739e6c087bf52c387f 172.22.0.9:6379 slots: (0 slots) slave replicates 0885f85b94f8ddc186f1eac8f532be532fb7f5b1[OK] All nodes agree about slots configuration.刪除後結果如上，在 Cluster 已經看不到 master1 蹤影了 小結Redis 官方對於 Cluster 支援還有說明文件寫得很棒，推薦大家去看 如果會有 Redis 為何使用 16384 當作 slot 數量可以參考作者回答的資料 why redis-cluster use 16384 slots 參考資料cluster-spec Redis cluster tutorial 此文作者：Daniel Shih(石頭)此文地址： https://isdaniel.github.io/redis-cluster-introduce-01/ 版權聲明：本博客所有文章除特別聲明外，均採用 CC BY-NC-SA 3.0 TW 許可協議。轉載請註明出處！ |
【本文地址】
公司简介
联系我们